|
In software development and product management, a user story is a description consisting of one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function. User stories are used with agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management. It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper notecard. A user story encapsulates the action of one function making it possible for software developers to create a vertical slice of their work. ==History== User stories originated with Extreme Programming (XP), whose first written description in 1998 only claimed that customers defined project scope "with user stories, which are like use cases". Rather than offered as a distinct practice, they were described as one of the "game pieces" used in the planning game. However, most of the further literature thrust around all the ways arguing that user stories are "unlike" use cases, in trying to answer in a more practical manner "how requirements are handled" in XP and more generally Agile projects. This drives the emergence, over the years, of a more sophisticated account of user stories.〔(【引用サイトリンク】publisher=Agile Alliance )〕 In 2001, Ron Jeffries proposed the well-known Three C's formula, i.e. ''Card, Conversation, Confirmation'', to capture the components of a user story:〔(【引用サイトリンク】author=Ron Jeffries )〕 *A ''Card'' (or often a Post-it note) is a physical token giving tangible and durable form to what would otherwise only be an abstraction; *A ''Conversation'' is taking place at different time and places during a project between the various stakeholders concerned by the given feature (customers, users, developers, testers, etc.), which is largely verbal but most often supplemented by documentation; *The ''Confirmation'', the more formal the better, ensures that the objectives the conversation revolved around have been reached finally. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「User story」の詳細全文を読む スポンサード リンク
|